The 640 MEG Shareware Studio 2

home *** CD-ROM | disk | FTP | other *** search

/ The 640 MEG Shareware Studio 2 / The 640 Meg Shareware Studio CD-ROM Volume II (Data Express)(1993).ISO / business / tuam103a.zip / TUAMSM.DOC < prev next >

Wrap

Text File | 1992-11-15 | 78KB | 1,817 lines

The Ultimate Account Management System Manager Version 1.03 August 1992 If you need support, we have an echoed conference on Salt Air carried at present by our support board, Salt Air, and TDS Intl. If you want to pick up this conf for our own reading, feel free to do so. We trust you like our new features, and please feed back any new ideas to us. I would like to thank Fred Clark as if it were not for his work, then PCBoard would not be here today. David Terry and all the staff at CDC also have condolences coming, as they were instrumental in creating PCBoard v14.5 and beyond. I would also like to take time to thank you for reviewing our product, and considering it as an option for distribution of bytes to your users. Please be so kind as to provide us with feedback as to what you think of the documentation, our product in general and its features. We consider providing you with a quality product that meets your needs of utmost importance. If this product fails to meet your needs, please let us know where we failed, what we could have done to make the product better, or why you chose not to use our product. We appreciate your time and effort in reading our documentation, and in trying our products. Please take time to read this file, and pay close attention to the operation of this system, especially in regards to the PWRD file. The improper use of PWRD file and this system can cause you some unexpected results. The PWRD settings will take control, and TUAM will NOT allot bytes to the user ! Disclaimer Ok, lets get through the legal stuff up front. Platinum Software, or any of its associates are not liable for any damages suffered as a result of use of this software, either by proper use or improper use. We assume no liability for any losses incurred, either financial or otherwise as a result of use of this software. We hold no responsibility for your inability to use this software due to your hardware configurations, software configurations, or any other reason not mentioned in this document. This software has been tested at our sites, and is being distributed in a beta format. You agree to assume full responsibility for any consequences incurred as a result of use or misuse of this software. Key Functions The following table list key functions available in the System Manager. F1 Help (Context sensitive - not in Beta release) Below is an example of pressing F1 key. [ Byte Editor ] [ F1 = Help ] R D E U E Usr ┌──[ Key Help ]──────────────────────────┐ x L s Lvl │ F10 - save changes │ p P t │ ESC - abort changes │ 1 │ ENTER - next field │ N N N 2 │ TAB/Shift TAB - next/previous field │ N N N 3 │ PgDn/PgUp - next/previous screen │ N N N 4 │ Down/Up - next/previous record │ N N N 5 │ Left/Right - move within field │ N N N 6 │ Home/End - start/end of field │ N N N 7 │ Insert - toggle insert mode │ N N N 8 │ Ctrl U - undo current field │ N N N 9 │ Ctrl Home/End - first/last field │ N N N 10 │ Ctrl Left/Right - word left/right │ N N N 11 │ Ctrl Y - delete to end of field │ N N N 12 │ Ctrl BS/T - delete word left/right │ N N N 13 │ Space - toggle Y/N (logical) field │ N N N 14 └────────────────────────────────────────┘ N N N 15 0 0 0 N Y N N N 16 0 0 0 N Y N N N [ The Ultimate Account Manager V1.03 ] F2 Help (Generic Help) not in beta releases. Up Arrow Up to next field above current location Dn Arrow Shift TAB Moves to previous field TAB Moves to next field ENTER Moves to next field ESC Discard any changes made in current session. You will be challenged when pressing ESC key. Will return to previous menu, or abort program depending upon level. PgUp Move between screens (Up) Will NOT write to file with Security File editor. TPA editor will write changes to file. PgDn Move between screens (Down) Will NOT write to file with Security File editor. TPA editor will write changes to file. F10 Will save current record, and exit to menu Ctrl Home First field on screen Ctrl END Last field on screen Ctrl U Undo Key - will undo the current field Ctrl - U will work on any field on current screen, however after using PgUp or PgDn, the Ctrl-U will not undo information automatically on screen. Insert Toggles between Insert and Overtype mode. Cursor will be underline in overtype and block in insert mode. Home Beginning of current field END End of text in current field Right Arrow Right one character in current field to end of field. Will NOT move to next field upon reaching end. Left Arrow Left one character in current field to beginning of field. Will NOT move to previous field upon reaching beginning of field. Ctrl Right Moves right one word in current field Ctrl Left Moves left one word in current field Backspace Backspaces one character Delete Deletes current character Ctrl Y Deletes from current position to end of field Ctrl T Deletes word to right (or from current position to end of current word) Ctrl Backspace Deletes word left. (or from current position to beginning of current word) Alt Rt Arrow Moves right one field, will roll around at end of screen. Alt Lft Arrow Moves Left one field, will roll around at beginning of screen. Resetting Data to Default Value If you wish to reset one or any number of fields while in a single screen, move the cursor to the field to be reset. While in the field to be reset, press CTRL-U, the original value will be returned to the field. This can be done as many times as you wish as long as you stay within the one security screen display. If you have changed screens (PGUP or PGDN) then the values are semi-permanent, and will have to be reset manually, or the changes can be aborted prior to save. Saving Data Upon moving from one screen to the other, the data will be saved in a temporary buffer area, however will not be saved to disk until you press F10 to save. Upon pressing ESC to exit, you will be warned of a possible loss of data, and asked if you wish to proceed. [ Byte Editor ] [ F1 = Help ] ┌───────────────────────────────────────────────────────────────┐ │ R D E U E │ │ Usr Initial Session Daily S s x L s │ │ Lvl KBytes KBytes KBytes T p p P t │ │ │ │ 1 0 0 0 N N N N N │ │ 2 0 0 0 N N N N N │ │ 3 ┌──[ Abort ]─────────────────────────┐N N N N │ │ 4 │ Are you sure you want to abort? N │N N N N │ │ 5 └────────────────────────────────────┘N N N N │ │ 6 0 0 0 N N N N N │ │ 7 0 0 0 N N N N N │ │ 8 0 0 0 N N N N N │ │ 9 0 0 0 N N N N N │ │ 10 0 0 0 N N N N N │ │ 11 2000000 500000 800000 N Y N N N │ │ 12 0 0 0 N Y N N N │ │ 13 0 0 0 N Y N N N │ │ 14 0 0 0 N Y N N N │ │ 15 0 0 0 N Y N N N │ │ 16 0 0 0 N Y N N N │ └───────────────────────────────────────────────────────────────┘ [ The Ultimate Account Manager V1.03 ] Acceptable key inputs are ASCII characters from 32 to 254 except where fields are prompting for specific input. System Manager Introduction The Ultimate Account System Manager opening screen provides you with one of eight options. You can move between the options by using the arrow keys to move up or down, or by simply pressing the first letter in the desired menu option. The highlighted option will be selected by pressing the <ENTER> key. The Ultimate Account Manager System Manager Version 1.03 ┌────────────────────────────────────┐ │ Main Menu │ │ │ │ User Editor │ │ Byte Editor │ │ Ratio Editor │ │ Time Editor │ │ Command Editor │ │ PWRD Editor │ │ Configuration Editor │ │ Exit T.U.A.M. SM │ │ │ └────────────────────────────────────┘ Platinum Software Development Copyright (C) 1992, All Rights Reserved Platinum Developer Key Central Ontario Data Systems Computer Information Service ╓──────────────────────────────────────────────────────────────────────────── ║ User Editor ║ ║ This option will allow editing of individual user account. ║ ║ Including such information as Security Level, Last Date On, ║ ║ Bytes and/or Time in User Account, etc. ║ ╟────────────────────────────────────────────────────────────────────────────╢ ║ Byte Editor ║ ║ This option allows setting up specific BYTE information per ║ ║ security level. ║ ║ These level settings WILL be overridden by any PWRD setting ║ ║ for the same security level. ║ ╟────────────────────────────────────────────────────────────────────────────╢ ║ Ratio Editor ║ ║ This option allows defining if Ratios are used per security ║ ║ level. ║ ║ ║ ║ Also defined here are amount of credit given for uploads for ║ ║ non-ratio accounts. (if any credit is given) ║ ║ ║ ║ Type of ratios are also sysop definable per security level. ║ ╟────────────────────────────────────────────────────────────────────────────╢ ║ Time Editor ║ ║ Allows editing of Daily Limits, Session Limits, and Initial ║ ║ Time granted per security level, as well as reset frequency. ║ ║ These settings will be overridden by any setting in PWRD ║ ║ for same security levels. ║ ╟────────────────────────────────────────────────────────────────────────────╢ ║ Command Editor ║ ║ This allows defination of individual command PER security ║ ║ level ! ║ ║ There is a default screen, which can be copied into any ║ ║ security level using ALT-D command when editing that level. ║ ╟────────────────────────────────────────────────────────────────────────────╢ ║ PWRD Editor ║ ║ Allows editing of PWRD file, similar to PCBoards editor. ║ ║ ALL settings in here will override the other settings for ║ ║ the same levels found elsewhere by TUAM. ║ ║ Please note we DO NOT edit PCBoards actual PWRD file, and ║ ║ it will remain in its original directory, in an untouched ║ ║ fashion. We edit similar data kept in another binary file ║ ║ for TUAM purposes. ║ ╟────────────────────────────────────────────────────────────────────────────╢ ║ Configuration Editor ║ ║ Various settings which are not security level, byte or ║ ║ time specific are kept inside this screen. ║ ╟────────────────────────────────────────────────────────────────────────────╢ ║ Exit TUAM ║ ║ Exit Editor and return to DOS ║ ╙────────────────────────────────────────────────────────────────────────────╜ User Information Editing [ User Editor ] [ F1 = Help ] User Number: 1 Name: ROBIN WELLS Security Level: 241 Expiry Date: 00-00-00 Expired Security Level: 240 Last Byte Reset: 11-14-92 Last Time Reset: 11-14-92 Last Date On: 11-14-92 Last Time On: 07:54 Zero Bytes: N Time Reset: Y Auto TPA Update: Y Initial Time: 0 Time Left in Account: 1440 Time Used Today: 0 Initial Bytes: 5120000 Bytes Left in Account: 5120000 Total Bytes Downloaded: 14143122 Total Bytes Uploaded: 32011503 Total Files Downloaded: 1178 Total Files Uploaded: 110 Bytes Downloaded Today: 0 [ The Ultimate Account Manager V1.03 ] User Number : This corresponds directly with the user number as defined in the PCBoard Users file. Name : This is the users name as found in the PCBoard USERS file. Security Level : Security level as in PCBoard USERS file. Expiry Date : Users Expiry Date. Last Byte Reset: The date the last Byte Account was reset by the system Last Time Reset: The date the last Time Account was reset by the system Last Date On: The last date the user was on this system Last Time On: The last time the user was on this system Zero Bytes: If set, this user will be granted ZERO "0" bytes for EACH session, regardless of any other settings. No other setting is changed, this allows a temporary turn off of bytes without changing any other user information if required by the sysop. Time Reset: This flag will normally be set to Yes "Y", however if set by the sysop to No "N", this user will not ever have their TIME account reset, regardless on any other settings for this user. Auto TPA Update : This will ensure that the users account is adjusted automatically if the users security file information changes. Use with caution, as if you set initial bytes manually for example, they will be reset to the security file defaults upon re-entry to the TUAM system if this flag is set. This flag can provide a great deal of extra automation, however it can also cause some grief that is difficult to track down if used incorrectly. Initial Time: Time placed into users account when - 1) The user first uses this system 2) A TIME reset is done for this user 3) This user changes security level 4) Some information in the security file is changed for this users level, and auto TPA update is set to Yes. Also can be used by sysop as a comment field to track how many bytes a user has purchased. Time Left in Account: Running total of users remaining time on system if using account time. Time Used Today: Time used on system today Initial Bytes: Bytes placed into users account when - 1) The user first uses this system 2) A BYTE reset is done for this user 3) This user changes security level 4) Some information in the security file is changed for this users level, and auto TPA update is set to Yes. Also can be used by sysop as a comment field to track how many bytes a user has purchased. Bytes Left in Account: Total bytes left in users account. This is increased by sysop, or by security level change, or by a BYTE reset taking place. Total Bytes Downloaded: Total bytes downloaded as defined in PCBoard USERS account. (last time user was through TUAM system) Total Bytes Uploaded: Total bytes uploaded as defined in PCBoard USERS account. (last time user was through TUAM system) Total Files Downloaded: As displayed in PCBoard USERS account. Total Files Uploaded: As displayed in PCBoard USERS account. Bytes Downloaded Today: As displayed in PCBoard USERS account. Saving Users Data Press F10 to save data in users field, if you press ESC to leave an edited field, or press PGUP or PGDN, you will be challanged with the following display. Last Reset Date: 10-25-92 ┌──[ Data has been changed ]──────┐ │ Do you want to save it? Y │ └─────────────────────────────────┘ Auto TPA Update: Y User Editor Specific Keys: Alt-F Find user name. Needs complete user name. Alt-J Jump to specific user number. [ Byte Editor ] [ F1 = Help ] R D U E Usr Initial Session Daily S s L x Lvl KBytes KBytes KBytes T p P p 81 1000 800 800 Q Y N N 93 1000 1000 1000 M Y N Y 177 1000 2000 0 N Y Y N 181 1000 0 0 N N N N 225 0 0 0 N N N N 231 500000 5000 5000 N Y Y N 239 0 5000 5000 N N N N 241 5000 3000 0 D Y Y N [ The Ultimate Account Manager V1.03 ] Explaination of various settings shown above: 81 1000 800 800 Q Y N N Level 81 will be granted 1 Meg when first using TUAM, upon Byte Reset, or when the security level is changed to 81 from a previous level. This user will be granted 800K per session with a daily limit of 800K. They will be Reset (RST) Quarterly, and will be granted the 1 Meg in their account upon that reset. The Display is enabled and will be displayed to the user upon login. Upload Credit for files is NOT given. (However user may still be on ratios, we will have to look at the ratio screen for that) ULP flag will simply grant credit for uploaded files and will place that credit as bytes in the users account. This user will NOT Expire (Exp) when their bytes in account reach zero bytes. (If Exp was set to Y, the Expiration Date would have been set to current date, and expired Security level copied into current level once bytes in account reached Zero) 93 1000 1000 1000 M Y N Y Level 93 will be granted 1 Meg when first using TUAM, upon Byte Reset, or when the security level is changed to 93 from a previous level. This user will be granted 1 Meg per session with a daily limit of 1 Meg. They will be Reset (RST) Monthly, and will be granted the 1 Meg in their account upon that reset. The Display is enabled and will be displayed to the user upon login. Upload Credit for files is NOT given. (However user may still be on ratios, we will have to look at the ratio screen for that) ULP flag will simply grant credit for uploaded files and will place that credit as bytes in the users account. This user will Expire (Exp) when their bytes in account reach zero bytes. The Expiration Date will be set to current date, and expired Security level copied into current level once bytes in account reached Zero 177 1000 2000 0 N Y Y N Level 177 will be granted 1 Meg when first using TUAM, upon Byte Reset, or when the security level is changed to 177 from a previous level. This user will be granted 2 Megs per session with no daily limit being imposed. This user can download as many 2 Meg sessions as they have time for in each day! The user account will NOT be Reset. The Display is enabled and will be displayed to the user upon login. Upload Credit for files is given. User will be granted files in their account for every upload sent to system. The amount of bytes to place in account is calcuated by multiplying the Byte Ratio times the bytes uploaded. NOTE: Even though the Byte Ratio value is used in ULP credit, this user is NOT on ratios. We will examine the Ratio screen later. (remember to look at Security level 177) This user will NOT Expire (Exp) when their bytes in account reach zero bytes. 181 0 0 0 N N N N This user gets no bytes initially in their account, but zero session and zero daily bytes. No display, no reset. Lets hope this user has some bytes in PWRD, or they are out of luck in getting files from this system. 231 500000 5000 5000 N Y Y N Similar to previous settings with 500 Meg in account with NO reset. Upload Processing (Credit) is ON. Display is ON. Session and Daily limits are 5 meg. Security Level of User (Usr Lvl) Current Security Level of user, when user security level matches, the fields associated with this level will be applied. Initialization KiloBytes (Initial KBytes) Kilobytes Account will be initialized with. Any value in here will be multiplied by 1024. Session KiloBytes (Session KBytes) This value is the default amount of Kbytes given to a user limited by some conditional values. Will be multiplied by 1024. #1 ) Base Baud rate, as mentioned below can increase or decrease this value. See Base Baud Rate #2 ) Factoring Value - as mentioned below can affect this value. #3 ) Daily Limits CAN NOT be exceeded, if they are lower than session bytes, or some bytes have been already downloaded today then daily limits will be honored. IF DAILY LIMITS IS SET TO 0, THEN IT IS ASSUMED THAT DAILY LIMITS WILL NOT BE ENFORCED. See also Daily Limits. #4 ) If Real Ratio is set, then the actual ratio is given rather than session bytes. NOTE: If Real Ratio is larger than session bytes or daily bytes, then both session and daily bytes will be imposed upon the limits. See also Daily Bytes, Session Bytes or Real Ratios. #5 ) If File Ratio and/or Byte ratio is set, and ratios are NOT in line, then zero bytes will be granted, regardless of session bytes. Example of session bytes with Base Baud rate and Factor Value: (Session Bytes * ((Current Baud Rate/Base Baud Rate) * (Factor Value/100))) ie: (1000000 * ((9600/2400) * (200 (factor)/100))) 1000000 * (( 4 ) * ( 2 )) 1000000 * 8 = 8000000 or -----> (1000000 * ((2400/2400) * (200 (factor)/100))) 1000000 * (( 1 ) * ( 2 )) 1000000 * 2 = 2000000 or -----> (1000000 * ((300/2400) * (200 (factor)/100))) 1000000 * (( .25 ) * ( 2 )) 1000000 * .5 = 500000 Now, set as 2:1 seems useless, however if factor is set to 125 for example, then it would be easier to use than say an odd baud rate in base baud rate. ie: (1000000 * ((9600/2400) * (125 (factor)/100))) 1000000 * (( 4 ) * ( 1.25 )) 1000000 * 5 = 5000000 or -----> (1000000 * ((2400/2400) * (125 (factor)/100))) 1000000 * (( 1 ) * ( 1.25 )) 1000000 * 1.25 = 1250000 or -----> (1000000 * ((300/2400) * (125 (factor)/100))) 1000000 * (( .125 ) * ( 1.25 )) 1000000 * .25 = 156250 Daily KiloBytes (Daily KBytes) This value WILL NOT be exceeded in one calendar day, regardless of other settings or values. This value will be multiplied by 1024. IF DAILY LIMITS IS SET TO 0, THEN IT IS ASSUMED THAT DAILY LIMITS WILL NOT BE ENFORCED. This does not normally have the same limitations as PCBoard's bytes limits on midnight roll over ! However, these same limitations can apply in certain situations, although they are unlikely. This means you should be able to let a user go past midnight, and still get full bytes the following day ! Reset Periods: (Rst) This flag can be set to either N, D, W, M Q, S or Y for Not used, Daily, Weekly, Monthly, Quarterly, Semi-Annually or Yearly. The system will reset account bytes to initial bytes as defined in the security file for users security level based upon this flag. The interval period for this flag is per user, and is calculated from the time the user first started using the TUAM system. Yearly If set to "Y" for yearly resets, the account bytes will be reset to initial bytes on the annual anniversary of the date shown as last reset date. This is not based upon a day of the week, such as Sunday or Monday, but rather on the day the initial login or last reset was done. This can be affected by either modifying the last reset date. Semi-Annual If set to "S" for semi-annual resets, the account bytes will be reset to initial bytes on the semi-annual anniversary of the date shown as last reset date. This is not based upon a day of the week, such as Sunday or Monday, but rather on the day the initial login or last reset was done. This can be affected by either modifying the last reset date. Quarterly If set to "Q" for quarterly resets, the account bytes will be reset to initial bytes on the quarterly anniversary of the date shown as last reset date. This is not based upon a day of the week, such as Sunday or Monday, but rather on the day the initial login or last reset was done. This can be affected by either modifying the last reset date. The days in a quarter depend upon which months are used, they are actual month lengths and not a fixed number of days. ie: Feb 6th to May 6th is one quarter. Monthly If set to "M" for yearly resets, the account bytes will be reset to initial bytes on the monthly anniversary of the date shown as last reset date. This is not based upon a day of the week, such as Sunday or Monday, but rather on the day the initial login or last reset was done. This can be affected by either modifying the last reset date. Weekly If set to "W" for yearly resets, the account bytes will be reset to initial bytes on the weekly anniversary of the date shown as last reset date. This is not based upon a day of the week, such as Sunday or Monday, but rather on the day the initial login or last reset was done. This can be affected by either modifying the last reset date. Daily If set to "D" for yearly resets, the account bytes will be reset to initial bytes on a daily basis. The results of this can not be adjusted, as last reset date is set each time online, and the reset takes place daily. Daily accounts will however not normally have the midnight rollover loss of bytes associated with PCBoard ! As a matter of fact, a user could be granted both days bytes during one login if so desired. The SysOp would have to let the user know this was possible, and how to accomplish it. This flag makes TUAM operate exactly the same as PCBoard's PWRD file with the added flexibility of upload credits for a specific security level, while not affecting the other levels, as UPCRED or BYTECRED would do. Display (Dsp) If turned ON the Display User Information at Login is handled by the TUAM door. If turned OFF the Display User Information at Login is disabled in TUAM. Upload Processing (ULP) This is a somewhat critical flag, and should be used only after reading this documentation. The ULP flag will NOT provide for upload/download ratios, but will instead credit additional bytes in the user account for new uploads. The Byte Ratio is still used for the upload credit, however the actual ratio is NOT considered at all in the calculations. This provides for boards with Monthly or Annual accounts to reward users for uploads. This provides boards that call out long distance to gather files themselves, and have pay members, to in effect 'pay' or reward members for contributing the system. This flag should be used with some degree of caution however, as some users will upload any and all files to obtain additional bytes. This problem should not be as severe in this case as with true ratio systems however, as users are just obtaining 'additional' bytes. Expire User (Exp) If this flag is set, user will expire when Bytes in account reach Zero bytes. The expiration date will be set to current date, and Expired Security Level will be copied into Current user level. File Ratios File and Byte ratios are provided for the user and are configurable by the SysOp. The SysOp can adjust the ratio required (1:1, 2:1, 3:1, etc) to be maintained by the File Uploads. This provides a File Ratio Enforcement as well as a bytes distribution system. If the Files are in line then the Session bytes are given to the user. ( this can be over ridden by the daily bytes field, based upon the daily bytes setting, and total bytes downloaded by user today ) If the File Ratio Fails, NOF will be displayed to the user, and zero bytes will remain for session. We have included @WAIT@ in the demonstration file to keep the screen displayed for the userr Byte Ratio File and Byte ratios are provided for the user and are configurable by the SysOp. The SysOp can adjust the ratio required (1:1, 2:1, 3:1, etc) to be maintained by the Byte Uploads. This provides a Byte Ratio Enforcement as well as a bytes distribution system. If the Bytes are in line then the Session bytes are given to the user. ( this can be over ridden by the daily bytes field, based upon the daily bytes setting, and total bytes downloaded by user today ) If the Byte Ratio Fails, NOB will be displayed to the user, and zero bytes will remain for session. We have included @WAIT@ in the demonstration file to keep the screen displayed for the userr See Real Ratio below. NOTE : If both File Ratio and Byte Ratio are set, both levels MUST be maintained by the user for any bytes to be allocated in session. In all cases the daily bytes will control maximum for day if daily bytes is set. Upload Credits on Byte Accounts When Upload processing is turned on, any user who uploads bytes will be granted additional bytes in their account. This factor is adjusted by the byte ratio. Example : A user has 750,000 bytes remaining in their account, with a ULP flag set and byte ratio set at 3:1. They have just uploaded a 325,000 byte file. Their account now will contain 750,000 + ( 325,000 * 3 ) or 1,725,000 bytes. [ Ratio Editor ] [ F1 = Help ] File Byte Base Fac Batch Usr R Ratio Ratio Baud 1/ File Lvl T ?:1 ?:1 Rate 100 Limit 11 N 1 1 2400 100 0 12 N 0 0 0 0 0 81 S 2 2 0 0 50 87 R 2 2 0 0 50 177 N 0 2 2400 200 50 Ratio Type (RT) This flag allows defining ratio calculation type. There are three valid values. ( N/S/R ) N flag disables the ratio system for all users of specific security level. S flag sets ratios at Session Ratios for users of specific security level. R flag sets ratios at Real Ratios for users of specific security level. Session Ratios : ( S setting in RT ) Session Ratios will distribute bytes based upon setting in Session Bytes. If ratios are in line, the full session bytes will be allotted to the user, provided the daily flag is either NOT set, or user has not used total daily allotment. Daily Download Bytes will still control overall bytes per day unless this setting is set to zero, in which case Daily Limits will be disabled. Real Ratios : ( R setting in RT ) This option was provided to give you the ultimate in flexibility ! Now you can have bytes allocated on File/Bite ratio based upon the actual ratio rather than the allocated amount in session and daily limits. This option still requires the ratio to be in line prior to allotting bytes to the user. Real Ratios will distribute bytes based upon the following formula and conditions. First, all File and/or Byte ratios MUST be in line as set out by the SECURITY file. If BYTE ratio is NOT used, then Real Ratio WILL NOT function. Bytes under Real Ratio will be distributed using the following formula. ( Total Bytes Uploaded * Byte Ratio ) - Total Bytes Downloaded This means if a user has uploaded 100,000 bytes and has downloaded 100,000 bytes, with the ratio set at 2:1, then the following would be the bytes allocated. ( 100,000 * 2 ) - 100,000 = (200,000) - 100,000 or 100,000 bytes remaining. Or if a user uploaded 350,000 bytes, downloaded 500,000 bytes, using a ratio of 5:1.. Then .. ( 350,000 * 5 ) - 500,000 = 1,250,000 bytes remaining ! NOTE : All bytes allocated under Byte Ratio and/or File Ratio using either Session Bytes or Real Ratio system will comply with session byte and daily byte limits. This means that in the above situation of 1.25 meg remaining, if the session bytes were set at 800K and the daily bytes were set at 2 Meg. The user would be allotted 800K upon first login of the day, and would continue to get 800K or the Daily limit of 2 meg less daily download bytes until the daily maximum was reached. If ONLY the byte setting is used this can be used in a fashion we call Actual Ratios. The File Ratio is NOT considered in the calculation or allotment of bytes, therefore : if a user uploads 100K and downloads 300K with a ratio of 3:1, they would be allotted (100000 * 3) - 300000 = 0 bytes or if they uploaded 150K and download 300K they would be allotted (150000 * 3) - 300000 = 150000 bytes. File Ratio (File Ratio ?:1) This is the ratio required for the File Ratio to be enforced at. If set to 2:1 you will be granting two files for every one file received. If set to 1:1, you will be granting one file for every file given. A word on the side, our ratio system will run smoothly and cause no grief or be caused no grief if you are using PCBoard's UPCRED or BYTECRED flags for instant credit. Bear in mind however that PCBoard's credits will apply to ALL users, and TUAM will only credit based upon user levels in security file. Bytes will be granted based upon Session Bytes as listed in the security file. Session bytes and Daily limits will be honored in all ratio systems. For Real Ratios see Real Ratio further down in this documentation. Byte Ratio (Byte Ratio ?:1) This is the ratio required for the Byte Ratio to be enforced at. If set to 2:1 you will be granting two bytes for every one byte received. If set to 1:1, you will be granting one byte for every byte given. A word on the side, our ratio system will run smoothly and cause no grief or be caused no grief if you are using PCBoard's UPCRED or BYTECRED flags for instant credit. Bear in mind however that PCBoard's credits will apply to ALL users, and TUAM will only credit based upon user levels in security file. Bytes will be granted based upon Session Bytes as listed in the security file. Session bytes and Daily limits will be honored in all ratio systems. For Real Ratios see Real Ratio further down in this documentation. Base Baud Rate (Base Baud Rate) This is similar to the Base Baud rate as in the PCBoard PWRD file. If the Base Baud rate is set at 2400 baud, and a user logs in using 4800 baud, twice the bytes will be allotted for that session. ( the above is affected as well by the Factoring Value, as mentioned below ) Session bytes are doubled, tripled, etc using the Base Baud rate values. NOTE: Daily Limits are STILL enforced for all accounts, regardless of settings of Base Baud rates or Factoring Values. ( Unless Daily Limits are disabled by a zero setting ) Factoring Value for Base Baud Rate (Fac 1/100) A mathematical factoring value for base baud rate. This is a new concept to base baud rate, and allows you the sysop a better control over base baud rate than previously available. This is set in 1/100ths, meaning a value of 100 is equal to 1, a value of 125 is equal to 1.25 in mathematical terms. If the base baud rate is 2400 baud and the base baud rate is 0 (zero) or 100, then the factoring is done as done by PCBoard. As an example, if a user gets 100K at 2400 baud they would get 200K at 4800 baud, 400K at 9600 baud, etc. If however a 300 baud user was online, they would get only 12.5K or 1/8th the value of 100K. Factoring adds a new twist and multiplies or divides by the factor rate, rather than just by one as is the normal case. With factoring set to 200 (200/100ths) then the same user above at 2400 baud would still get 100K. However, a 4800 baud user would get 400K and a 9600 baud user would get 800K. Inversely, a 1200 baud user would get only 25K and a 300 baud user would get only 6.25K. This feature encourages higher speed and penalizes lower speeds to a greater degree. Batch File Limit This is the same value as defined in PCBoards PWRD Batch Limit. [ Time Editor ] [ F1 = Help ] R E Usr Initial Session Daily S x Lvl Time Time Time T p 1 61 61 61 D N 81 180 31 46 W N 91 61 61 61 D N 161 91 91 91 N Y 176 121 121 121 D N 241 1440 1440 1440 D N All settings in Time Editor WILL NOT be used if use Time is NOT set in Configuration Editor, and/or PWRD file has Time settings for specific security level. In above examples : 1 61 61 61 D N Security Level 1 has 61 minutes placed in account on reset or initial time through system. Reset is done DAILY. Session and Daily Time Limits are 61 minutes. There is NO Expiration of account when Time is used up. This Expiration flag is a critical one, as a user with no time can NOT access your system. 81 180 31 46 W N Security Level 81 has 180 minutes initial time, reset weekly. With NO Expiration. Session Time is 31 minutes, with daily of 46 minutes. 91 61 61 61 D N Security Level 81 has 61 minutes initial time, reset daily. With NO Expiration. Session Time is 61 minutes, with daily of 61 minutes. 161 91 91 91 N Y Security Level 161 has 91 minutes initial time, reset daily. With Expiration turned ON, this user will have current date copied into expiration date, and expired level copied into base level upon reaching zero time in account. Session Time is 91 minutes, with daily of 91 minutes. 241 1440 1440 1440 D N And finally, my own account ! Yes you can have 1440 minutes in a session with TUAM ! No more limation of 999 minutes, but why you ask.. well, why not ! By the way, if you can get more than 1440 minutes in a day with or without TUAM, let me know ! I need all the extra time I can get <grin>. Reset Periods are the same as in Bytes Editor but lets review them again. Reset Periods: (Rst) This flag can be set to either N, D, W, M Q, S or Y for Not used, Daily, Weekly, Monthly, Quarterly, Semi-Annually or Yearly. The system will reset account bytes to initial bytes as defined in the security file for users security level based upon this flag. The interval period for this flag is per user, and is calculated from the time the user first started using the TUAM system. Yearly If set to "Y" for yearly resets, the account bytes will be reset to initial bytes on the annual anniversary of the date shown as last reset date. This is not based upon a day of the week, such as Sunday or Monday, but rather on the day the initial login or last reset was done. This can be affected by either modifying the last reset date. Semi-Annual If set to "S" for semi-annual resets, the account bytes will be reset to initial bytes on the semi-annual anniversary of the date shown as last reset date. This is not based upon a day of the week, such as Sunday or Monday, but rather on the day the initial login or last reset was done. This can be affected by either modifying the last reset date. Quarterly If set to "Q" for quarterly resets, the account bytes will be reset to initial bytes on the quarterly anniversary of the date shown as last reset date. This is not based upon a day of the week, such as Sunday or Monday, but rather on the day the initial login or last reset was done. This can be affected by either modifying the last reset date. The days in a quarter depend upon which months are used, they are actual month lengths and not a fixed number of days. ie: Feb 6th to May 6th is one quarter. Monthly If set to "M" for yearly resets, the account bytes will be reset to initial bytes on the monthly anniversary of the date shown as last reset date. This is not based upon a day of the week, such as Sunday or Monday, but rather on the day the initial login or last reset was done. This can be affected by either modifying the last reset date. Weekly If set to "W" for yearly resets, the account bytes will be reset to initial bytes on the weekly anniversary of the date shown as last reset date. This is not based upon a day of the week, such as Sunday or Monday, but rather on the day the initial login or last reset was done. This can be affected by either modifying the last reset date. Daily If set to "D" for yearly resets, the account bytes will be reset to initial bytes on a daily basis. The results of this can not be adjusted, as last reset date is set each time online, and the reset takes place daily. Daily accounts will however not normally have the midnight rollover loss of time associated with PCBoard ! This flag operated time the same as PCBoard, with the added advantage of session time, and no loss of time due to midnight rollover. Exp is the same as in Bytes Editor, if set, the user will Expire when the time in the account reaches zero minutes. [ Command Editor ] [ F1 = Help ] User Commands Settings For Security Level == 7 A) Abandon Conference == Y Q) Quick Message Scan == Y B) Bulletin Listings == Y R) Read Messages == Y C) Comment to Sysop == Y S) Script Questionaires == Y D) Download a File == Y T) Transfer Protocol == Y E) Enter a Message == Y U) Upload a File == N F) File Directory == N V) View Settings == Y H) Help Functions == Y W) Write User Info == Y I) Initial Welcome == Y X) Expert Mode Toggle == Y J) Join a Conference == N Y) Your Personal Mail == Y K) Kill a Message == Y Z) Zippy DIR Scan == N L) Locate File Name == N CHAT Between NODEs == N M) Mode (graphics) == Y OPEN a DOOR == Y N) New Files Scan == N TEST a File == N O) Operator Page == Y USER Search/Display == N P) Page Length == N WHO is On Another Node == N EDIT Your Own Messages == Y Batch File Transfers == N Expire on Reg Exp Date == Y Batch Limit == 0 [ The Ultimate Account Manager V1.03 ] The same User levels as defined in PCBoard manual, except we have ONE for each level if required ! The only difference is Expire on Reg Exp Date. Of course you want to Expire on Expiration Date you say! But, this will also copy the Expired Security Level into the Base Security Level for the specific user, something that normally requires running PCBSM to do! If you are editing a level, and wish to copy the default level, press ALT-D when in the command editor. [ PWRD Editor ] [ F1 = Help ] Base Usr Baud Batch Lvl Password Time KBytes Rate Limit 49 0 0 0 50 51 0 2000 0 50 130 90 1000 0 50 Not much explanation need here, the same fields as in PCBSetup. VERY IMPORTANT !! If users security level has any information other than zero bytes in the PWRD file, then TUAM will ignore the user, and allow them to have the same bytes as indicated in the PWRD file. TUAM will also display the bytes allowed in this session for the user as provided by the PWRD file. ( NOTE : TUAM will ONLY display the user info if the "Display User Info at Login" is set to NO in PCBOARD.DAT, and the Display User Info is set to YES in the TUAM Security File. ) See Display User Info section in this documentation for more detailed explanation. [ Configuration Editor ] [ F1 = Help ] Max Additional Levels 9 Use Time Levels Y KByte Threshold 50 Use Command Levels Y [ Default Commands ] A) Abandon Conference == N Q) Quick Message Scan == Y B) Bulletin Listings == Y R) Read Messages == Y C) Comment to Sysop == Y S) Script Questionaires == Y D) Download a File == Y T) Transfer Protocol == Y E) Enter a Message == Y U) Upload a File == N F) File Directory == N V) View Settings == Y H) Help Functions == Y W) Write User Info == Y I) Initial Welcome == Y X) Expert Mode Toggle == Y J) Join a Conference == N Y) Your Personal Mail == Y K) Kill a Message == Y Z) Zippy DIR Scan == N L) Locate File Name == N CHAT Between NODEs == N M) Mode (graphics) == Y OPEN a DOOR == Y N) New Files Scan == N TEST a File == N O) Operator Page == Y USER Search/Display == N P) Page Length == N WHO is On Another Node == N EDIT Your Own Messages == Y Batch File Transfers == N [ The Ultimate Account Manager V1.03 ] Command Editor Specific Keys: Alt-J Jump to specific security level. Alt-D Copy Default command settings from configuration editor into current security level. Max Additional Levels VERY IMPORTANT : If you use sliding security levels, the levels MUST be adjacent to each other. In other words ALL levels must be entered in a SORTED manner, with lowest level at the top. Versio 2 of TUAM will automatically sort the PWRD, Byte and Time files as they are saved to disk. In PCBSetup under your Conference Setup, you will see Additional Conference Security in each Conference setup screen. Place the highest level of additional Conference Security you have alloted in the Max Additional Levels area. Please note that the Intitial Bytes and Upload Processing will be calculated ONLY on the Base Security Level of the user and not the additional levels. If used, the user will gain the additional security when joining the selected conference(s). The user will then take on the Time and Bytes as alloted in the new Conference IF (and only if) the Read PWRD on Conference Join. This is shown below in a screen of PCBSetup Options #1 screen. If set to Y in PCBSetup the following will apply: "Sometimes when a user joins another conference, his or her security level is augmented. By consequence of this field, the PWRD file is scanned to provide not only changed security, but additional time, downloadable kilobytes, and batch limits." If set to N in PCBSetup "Although a user's security level is changed after joining a conference, he or she retains the limits previously assigned from the initial login. *** This additional feature will allow using Account Bytes in some *** Conferences, default PWRD settings in others, ratios in others, *** and FILE number limit only in still others! Shown below is an example of a Conference Setup Screen with the Additional Cof Security pointed out. ──────┐ ┌──────┘ --------------------------------------------│----------------------------------Ü │ #274 │ Conference Name : Shareware │ Make All Uploads Private : N Public Conference : Y ┌────┘ Make All Messages Private : N Req. Security if Public : 0 │ Echo Mail in Conference : Y Auto-Rejoin into this Conf : N └───>> Additional Conf Security : 1 Allow Viewing Conf Members : N Additional Conf Time : 0 Number of Message Blocks : 1 Name/Loc of MSGS File : R:\ILINK\SHAREWAR Name/Loc of Users Menu : N:\PCB\GEN\MAILMNU Name/Loc of Sysop Menu : N:\PCB\GEN\MAILMNU Name/Loc of NEWS File : N:\PCB\GEN\PUBLIC Sort Name/Loc Upload DIR File Location of Uploads Public Upld: 2 : : Private Upld: 2 : : Menu Listing Path/Name List File Doors : : Bulletins : : Scripts : : Directories : : Download Paths (listing only) : 07:11:26 10-26-92 F1 help caps: OFF num: ON ins: OFF Shown below is PCBSetup Options #1 screen, with Read PWRD File on Conf Join highlighted. ──────────────────────┐ │ -----------------------------------------------------│------------------------- │ Options #1 │ ┌──────────────┘ Disable Message Scan Prompt : Y │ Display NEWS Only if Changed : Y Disable 3-minute Screen Clear : N │ Display User Info at Login : N Disable Registration Edits : N │ Include 'Uploaded By' in Desc : N Disable High-ASCII Filter : N │ Verify Files Uploaded : Y Disable NS Logon Feature : N │ Allow Local SHELL to DOS : Y Disable Password Check (DOS) : Y │ Pre-load PCBTEXT File : N Multi-Lingual Operation : Y │ Pre-load CNAMES File : N Disable Full Record Updating : Y │ Use NEWASK+Standard Questions : N Run System as a Closed Board : N │ Allow One Name Users : N Use Non-Graphics Mode Only : N │ Log Caller Number to Disk : N Exit to DOS After Each Call : N │ Log Connect String to Disk : Y Eliminate Screen Snow in PCB : N │ Log Security Level to Disk : Y Allow ESC Codes in Messages : Y └──>>Read PWRD on Conference Join : Y Allow Carbon-Copy Messages : Y Confirm Caller Name / Address : N Validate TO: Name in Messages : Y Allow Password Failure Comment : Y Enforce Daily Time Limit : Y Warning on Logoff Command : N Keyboard Timeout (in min, 0=disable) : 5 Max Number of Lines in Scrollback : 50 Number of Upload Description Lines : 8 07:24:03 10-26-92 F1 help caps: OFF num: ON ins: OFF KByte Threshold With Accounts running and Ratios on the same level you run into one small difficulty. If a user is granted 1 meg for example in their account and is on ratios otherwise. The ratios will NOT start until the account runs out of bytes, however, the user may exhaust 999,900 bytes, leaving 100 bytes in the account. Now, ratios will NEVER start, and the user CAN NOT use up the remaining 100 bytes ! This Threshold is the number of KBytes that will be granted once the user account drops below this level, but is higher than zero. It defaults to 50K. This means when a user has between 0 bytes and 50K they will be given 50K in the session automatically. Once the bytes drop below zero however, they will be adjusted to equal zero. At this point the user will remain at zero, and be unable to download, Expire, be on ratios, or whatever you have defined. Use Time Levels If selected, TUAM will use Time as defined in Time Editor unless there is Time in PWRD for selected user. If turned OFF, Time will NOT be used. (Time MUST be in PWRD if turned OFF) If you use TIME levels, YOU MUST use TUAMLOFF. Please read the TUAMLOFF doc file. Use Command Levels If selected, the Command levels as defined in the Command Editor will be used. If the user DOES NOT have a command level set up, they WILL NOT be able to access the system! If you are using Time, and have not defined a level, the user will be granted the following commands only. If you use Command Levels YOU MUST use TUAMLOFF, please read the TUAMLOFF document file. G - Goodbye I - Initial Welcome OPEN - Open a DOOR C - Comment to Sysop Auto Help Screens TUAM has many auto-help screens, a few of which are shown here. [ Byte Editor ] [ F1 = Help ] ┌────────────────────────────────────────────────────────────────┐ │ R D E U E │ │ Usr Initial Session Daily S s x L s │ │ Lvl KBytes KBytes KBytes T p p P t │ │ │ │ 1 0 0 0 N N N N N │ │ 2 ┌─[ Auto Help ]────────────────┐ N N N N │ │ 3 │ The Reset Frequency can be: │ N N N N │ │ 4 │ Space or N - no reset │ N N N N │ │ 5 │ D - daily │ N N N N │ │ 6 │ W - weekly │ N N N N │ │ 7 │ M - monthly │ N N N N │ │ 8 │ Q - quarterly │ N N N N │ │ 9 │ S - semi-annually │ N N N N │ │ 10 │ Y - yearly │ N N N N │ │ 11 200└──────────────────────────────┘ Y N N N │ │ 12 0 0 0 N Y N N N │ │ 13 0 0 0 N Y N N N │ │ 14 0 0 0 N Y N N N │ │ 15 0 0 0 N Y N N N │ │ 16 0 0 0 N Y N N N │ └────────────────────────────────────────────────────────────────┘ [ The Ultimate Account Manager V1.03 ] [ Byte Editor ] [ F1 = Help ] R D E U E Usr Initial Session Daily S s x L s Lvl KBytes KBytes KBytes T p p P t 1 0 0 0 J N N N N 2 ┌─[ Auto Help ]────────────────┐ N N N N 3 │ The Reset Frequency can be: │ N N N N 4 │ Space or N - no reset │ N N N N 5 │ D - daily │ N N N N 6 │ W - weekly │ N N N N 7 │ M - monthly │ N N N N 8 │ Q - quarterly │ N N N N 9 │ S - semi-annually │ N N N N 10 │ Y - yearly │ N N N N 11 200└──────────────────────────────┘ Y N N N 12 0 0 0 N Y N N N 13 0 0 0 N Y N N N 14 0 0 0 N Y N N N 15 0 0 0 N Y N N N 16 0 0 0 N Y N N N [ The Ultimate Account Manager V1.03 ] [ Ratio Editor ] [ F1 = Help ] File Byte Base Fac Batch Usr R Ratio Ratio Baud 1/ File Lvl T ?:1 ?:1 Rate 100 Limit 1 T 0 0 0 0 0 2 ┌──[ Auto Help ]─────────────────────┐ 3 │ The Ratio Type can be: │ 4 │ Space or N - no ratios │ 5 │ S - session bytes │ 6 │ R - real ratio (calculated) │ 7 └────────────────────────────────────┘ 8 N 0 0 0 0 0 9 N 0 0 0 0 0 10 N 0 0 0 0 0 11 N 1 1 2400 100 0 12 N 0 0 0 0 0 13 N 0 0 0 0 0 14 N 0 0 0 0 0 15 N 0 0 0 0 0 16 N 0 0 0 0 0 [ The Ultimate Account Manager V1.03 ] Deposit Doors While we do not wish to take away from Deposit Doors, they may become redundant with our system in place. Depending upon how your users are given bytes a Deposit Door is not necessarily needed. I personally do still run Cam DeBucks Deposit Door however, providing certain users the ability to store only time, other the ability to store bytes and time, and still others no storage at all. If the user is configured with the Initial KBytes the same as you would like for a daily limit, and reset is set to DAILY, then a Depository Door will operate the same as it does for PCBoard. If a user is set for Annual bytes for example, a depository door is not needed. However the user of a depository will not seriously cause any problems to any account regardless of how it is set up. Once the bytes are stored in the deposit door they will be removed from the user account for that session. It will be possible in theory however to gain the maximum amount allowed in the deposit door as extra bytes above those in the users account. This would be done by waiting to expire, keeping full bytes in the account, and then withdrawing the bytes. This will be rectified if you set the expired security level in the deposit door to remove the bytes upon expiration of the users account. However, some deposit doors do not properly use the expired security level after the expired date, but continue to user the normal level. This can be prevented if you run PCBSM in an event and copy expired into the normal security area. TUAM will expire users if Exp flags are set, removing this problem in other doors. TUAM will look at both security levels, and use the proper one based upon the expiration date found in the users file. Beta Test Sites We are currently searching for some reliable beta sites for version 2 of TUAM. If you are interested, give us a call, we will consider all applicants. However, all applicants will not necessarly be selected as beta sites. TUAM v2 will include o Password Control o File Accounts o Message Accounts o Multiple security level configurations o Conference to join on login o Conference to join upon logoff o Password Database (for each user) o Network SysOp flag o Added flexibility on expiration of accounts o Estimated Expiration Dates o 26 Group Accounts o 10 Groups per User Account o Group Conferences o Minimum Password Length o Password Validation o Password Change forced by system based on sysop setting per security level. o Password Change override flag per individual user Support BBS Information Platinum Software has chosen Central Ontario Data Systems as its support board. The board has given us the privilege to log on regularly and answer all questions and process ordering information. All orders will be processed within 48 hours under normal conditions, other conditions may prevail, but you will be left ample notice if conditions change. Our support boards phone number is : (705) 722-8194, (705) 728-5815 (705) 835-6448 Central Ontario Data Systems has given us the unique ability to have our own bulletin board. We wish to express our thanks for this. Upon entering the system, you will only see a brief hint that you have reached Central Ontario Data Systems, and be instantly placed into Platinum Software Development Support Board. All of our files are in the Main Board. As a matter of fact, we have at this time seen no reason to add extra conferences to this board. The board is using an instant registration system (InstaReg) to allow you immediate2 access to the system and the support Conference upon first call. You will be provided with a MENU to select your registration level. BE SURE to select Platinum Software Support at this Menu. Upon completion of the registration, you will be placed into the Support Area of the board. The support Conferences will be 1995 and 1998. Your personal key file is available by sending in a cheque or money order to the above address. Both U.S. and Canadian cheques are processed. Sorry, we can not accept currencies other than US or Canadian dollars. Visa registration is accepted either online, or by filling in and mailing the form enclosed in the package. ( VISA.FRM ) We would like to pass along our thanks to the authors of several products who have made our life both more enjoyable, and much easier. Clark Development - PCBoard - PCB Development Kit - InstaReg (Registration Door) Please use the registration form ( REGISTER.FRM ) for cheque or money order forms. Please ensure your bulletin board name is spelled EXACTLY as in PCBSetup, the key file MUST match. Personal cheques will have a 10 day delay on processing prior to the generation of the key file (online) or mailing one back to you. This will allow sufficient time for the cheque to be processed by the banks. Visa orders placed online will be authorized with the key file being generated within 48 hours. Other Forms of Support: We can be reached on Salt Air, TDS International Network, ILink, RIME, Intelec or NANet PCBoard Conferences or on our own support board. All of our code is posted upon release on Salt Air and on TDS International Network. Product Credit : PCBoard v14.5 - Clark Development Corp PCBToolKit - Clark Development Corp Microsoft - MS-DOS 3.30, MS-DOS 5.0 Compaq - DOS 3.31 Novell - Netware 3.31, Netware 2.2 ArtiSoft - LanTastic 4.1 Licence Agreement The Ultimate Account Manager, its accompanying programs, documentation and associated files are Copyrighted (C) 1992 by Platinum Software Development. All rights reserved. You may not engage in, nor permit third parties to engage in any of the following : A ) Altering the software, the documentation, the key files or any other files associated with or supplied with The Ultimate Account Manager. B ) Attempting to reverse engineer, disassemble, decompile any of the software, key files or associated files in any way or by any means, either electronic, mechanical or manually. C ) Granting licences, sub-licences, leases or any rights of any kind of this software to others. D ) Selling or giving away key files without proper notification to Platinum Software Development. Platinum Software grants you a licence to use this software as long as you agree to meet, and continue to meet all the above conditions. Any present or future violations of any of the above conditions will result in the termination of your licence to use this software. Upon termination for any reason, you must immediately stop using this software, and destroy all copies of the key files in your possession. Platinum Software reserves the right to cancel your licence at any time for any violations incurred that may not be listed in this documentation. Cancellation of licence due to violation of agreement will forfeit your ability to use this product, and any or all fees paid to use this product.